Skip to content

Update functions-how-to-azure-devops to clear warning message #127376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 29, 2025
Merged

Update functions-how-to-azure-devops to clear warning message #127376

merged 1 commit into from
Aug 29, 2025

Conversation

nikmaxott
Copy link
Contributor

Using prune --production gives a warning to switch to --omit=dev I have done this

@nikmaxott
Update functions-how-to-azure-devops to clear warning message
34cc1bb 
Using prune --production gives a warning to switch to --omit=dev I have done this
@prmerger-automator prmerger-automator bot requested a review from juliakm July 14, 2025 15:48
@prmerger-automator PRMerger Automator
Copy link
Contributor

@nikmaxott : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@nikmaxott
Copy link
Contributor Author

nikmaxott commented Jul 14, 2025 •
edited
Loading

Also as an aside, why are we publishing and then downloading to the artifacts, can we switch to just publishing and then using $(System.DefaultWorkingDirectory)/**/*.zip as the package. I am happy to create a PR for this change

@learn-build-service-prod Learn Build Service (PROD)
Copy link
Contributor

Learn Build status updates of commit 34cc1bb:

✅ Validation status: passed

File Status Preview URL Details
articles/azure-functions/functions-how-to-azure-devops.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@juliakm

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team @

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jul 14, 2025
@v-dirichards
Copy link
Contributor

@juliakm

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@juliakm
Copy link
Contributor

juliakm commented Aug 29, 2025

#sign-off

@nikmaxott Thanks for your contribution! We generally make publish and download separate in case someone is using the article as a model when building a pipeline with multiple stages.

@ttorble ttorble merged commit 48e6224 into MicrosoftDocs:main Aug 29, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
1 more reviewer

@juliakm juliakm juliakm approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees

@juliakm juliakm

Labels
aq-pr-triaged tracking label for the PR review team azure-functions/svc Change sent to author ready-to-merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@nikmaxott @v-dirichards @juliakm @ttorble